Device, system and method of selectively aborting reception of wireless communication packets

ABSTRACT

Some demonstrative embodiments include devices, systems and/or methods of selectively aborting reception of wireless communication packets. For example, a receiver may at least partially process a portion of a wireless communication packet, to determine based on the portion of the communication packet whether the packet is intended to be received by the receiver and, if the packet is not intended to be received by the receiver, to abort processing of a remainder of the communication packet by one or more components of a physical layer of the receiver. Other embodiments are described and claimed.

BACKGROUND

The battery life of cellular telephone devices having Wireless LocalArea Network (WLAN) capabilities, in terms of standby time or talk time,is generally much shorter than the battery life of comparable cellulartelephones devices that do not have WLAN capabilities. In addition toother factors, random access mechanisms utilized by WLAN systems, is amajor contributor to the fast battery drainage of such devices. Somenetworking systems, such as systems in accordance with the IEEE 802.11and 802.3 standards, rely on carrier-sense multiple access (CSMA) forchannel access. In these systems, when one node (e.g., a wirelessdevice) transmits communication packets, all nodes (e.g., wirelessdevices) within range of the transmitting node/device receive thepackets. Then, in many systems, each node/device decodes the entirepacket, e.g., by processing the entire packet at a Physical Layer (PHY)of the decoding device, and checks. After decoding the entire packet, aMedium Access Control (MAC) layer of the decoding device checks, forexample, a MAC header of the packet, to determine whether the packet isintended for the decoding node, e.g., if the packet is a broadcastpacket, a multicast packet intended for a network including the decodingnode, or a unicast packet intended for reception by the decoding node.If the packet is intended to be received by the decoding node, a lowerMAC layer of the decoding device passes the packet to an upper MAC layerfor further processing. Otherwise, the lower MAC layer “drops” thepacket from further processing. The lower MAC layer is usuallyimplemented in micro-code (“uCode”), whereas the upper MAC layer isusually implemented in a driver of the decoding node/device.

However, in many of today's implementations, the data packet is droppedonly after the entire packet has been decoded at the PHY layer andpassed to the lower MAC layer. Because the PHY layer usually consumesmost of the energy in a communication chipset and because communicationchipsets generally spend more time receiving than transmitting, theenergy consumed by reception of irrelevant packets has become aparticularly significant factor in battery drainage. Furthermore, thetrend of increased energy consumption in reception of irrelevant packetsis becoming even more significant with the development of newcommunication devices with advanced capabilities that are able toreceive larger communication packets.

Many packets are long packets, containing a substantial amount ofinformation. For example, some communication technologies, such as theIEEE 802.11 and 802.3 standards, can transmit jumbo frames. For example,the IEEE 802.11n standard defines two frame aggregation schemes, thatis, A-MSDU and A-MPDU, which have a frame size limit of 4K or 8K octetsand 65,535 octets respectively.

BRIEF DESCRIPTION OF THE DRAWINGS

For simplicity and clarity of illustration, elements shown in thefigures have not necessarily been drawn to scale. For example, thedimensions of some of the elements may be exaggerated relative to otherelements for clarity of presentation. Furthermore, reference numeralsmay be repeated among the figures to indicate corresponding or analogouselements. The figures are listed below.

FIG. 1 is a schematic block diagram illustration of a system, inaccordance with some demonstrative embodiments.

FIG. 2 is a schematic illustration of a wireless communication packet,in accordance with some demonstrative embodiments.

FIG. 3 is a schematic flow-chart illustration of a method of selectivelyaborting reception of wireless communication packets, in accordance withsome demonstrative embodiments.

FIG. 4 a is a schematic block diagram illustration of a first type of awireless communication packet to be received, in accordance with somedemonstrative embodiments.

FIG. 4 b is a schematic block diagram illustration of a second type of awireless communication packet to be received, in accordance with somedemonstrative embodiments.

FIG. 5 is a schematic illustration of an article of manufacture, inaccordance with some demonstrative embodiments.

DETAILED DESCRIPTION

In the following detailed description, numerous specific details are setforth in order to provide a thorough understanding of some embodiments.However, it will be understood by persons of ordinary skill in the artthat some embodiments may be practiced without these specific details.In other instances, well-known methods, procedures, components, unitsand/or circuits have not been described in detail so as not to obscurethe discussion.

Discussions herein utilizing terms such as, for example, “processing”,“computing”, “calculating”, “determining”, “establishing”, “analyzing”,“checking”, or the like, may refer to operation(s) and/or process(es) ofa computer, a computing platform, a computing system, or otherelectronic computing device, that manipulate and/or transform datarepresented as physical (e.g., electronic) quantities within thecomputer's registers and/or memories into other data similarlyrepresented as physical quantities within the computer's registersand/or memories or other information storage medium that may storeinstructions to perform operations and/or processes.

The terms “plurality” and “a plurality” as used herein include, forexample, “multiple” or “two or more”. For example, “a plurality ofitems” includes two or more items.

The terms “powering down” and “power down” as used herein with relationto a device and/or a component may refer, for example, to reducing,diminishing, shutting down, powering off, turning off and/or switchingoff the electrical current to the device and/or component, and/or toswitching the device and/or component to operate at a sleep mode, areduced-power mode, a stand-by mode and/or any other operation modewhich consumes less power than required for full and/or normal operationof the device and/or component. For example, powering down a receiver, acomponent of a receiver, a Physical Layer (PHY) of a receiver, aRadio-Frequency (RF) component of a receiver, and/or a Baseband (BB)component of a receiver may include reducing, diminishing, shuttingdown, powering off, turning off and/or switching off the electricalcurrent to the receiver, the component of the receiver, the PHY of thereceiver, the RF component of the receiver, and/or the BB component ofthe receiver; and/or to switching the receiver, the component of thereceiver, the PHY of the receiver, the RF component of the receiver,and/or the BB component of the receiver to operate at a sleep mode, areduced-power mode, a stand-by mode and/or any other operation modewhich consumes less power than required for full operation, e.g., forfull reception, handling, decoding and/or processing wirelesscommunication signals.

The terms “powering up” and “power up” as used herein with relation to adevice and/or a component may refer, for example, to enhancing,resuming, turning on and/or switching on the electrical current to thedevice and/or component and/or to changing the device and/or componentfrom sleep mode, stand by mode or any other operation mode, whichconsumes less power than required for full reception and/or normaloperation of the device and/or component, to operational mode. Forexample, powering up a receiver, a component of a receiver, a PHY of areceiver, a RF component of a receiver, and/or a BB component of areceiver may include enhancing, resuming, turning on and/or switching onthe electrical current to the receiver, the component of the receiver,the PHY of the receiver, the RF component of the receiver, and/or the BBcomponent of the receiver; and/or to changing the receiver, thecomponent of the receiver, the PHY of the receiver, the RF component ofthe receiver, and/or the BB component of the receiver from sleep mode, areduced-power mode, a stand-by mode and/or any other operation modewhich consumes less power than required for full operation tooperational mode, e.g., for full reception, handling, decoding and/orprocessing wireless communication signals.

The term “portion of a packet” may refer, for example, to a header of apacket, a preamble of a packet and/or to any other suitable part,segment, and/or fragment of a packet, which contains informationregarding the packet and/or regarding the content of the packet. Forexample, the portion of the packet may include a physical layerconvergence procedure (PLCP) header of the packet, a Medium AccessControl (MAC) header of the packet, a PLCP preamble of the packet, andthe like.

Some embodiments may be used in conjunction with various devices andsystems, for example, a Personal Computer (PC), a desktop computer, amobile computer, a laptop computer, a notebook computer, a tabletcomputer, a server computer, a handheld computer, a handheld device, aPersonal Digital Assistant (PDA) device, a handheld PDA device, anon-board device, an off-board device, a hybrid device, a vehiculardevice, a non-vehicular device, a mobile or portable device, a consumerdevice, a non-mobile or non-portable device, a wireless communicationstation, a wireless communication device, a wireless Access Point (AP),a wired or wireless router, a wired or wireless modem, a video device,an audio device, an audio-video (A/V) device, a Set-Top-Box (STB), aBlu-ray disc (BD) player, a BD recorder, a Digital Video Disc (DVD)player, a High Definition (HD) DVD player, a DVD recorder, a HD DVDrecorder, a Personal Video Recorder (PVR), a broadcast HD receiver, avideo source, an audio source, a video sink, an audio sink, a stereotuner, a broadcast radio receiver, a flat panel display, a PersonalMedia Player (PMP), a digital video camera (DVC), a digital audioplayer, a speaker, an audio receiver, an audio amplifier, a gamingdevice, a data source, a data sink, a Digital Still camera (DSC), awired or wireless network, a wireless area network, a Wireless VideoArea Network (WVAN), a Local Area Network (LAN), a Wireless LAN (WLAN),a Personal Area Network (PAN), a Wireless PAN (WPAN), devices and/ornetworks operating in accordance with existing IEEE 802.11 (IEEE802.11-1999: Wireless LAN Medium Access Control (MAC) and Physical Layer(PHY) Specifications), 802.11a, 802.11b, 802.11g, 802.11h, 802.11j,802.11n, 802.16, 802.16d, 802.16e, 802.16f, standards (“the IEEE 802standards”) and/or future versions and/or derivatives thereof, devicesand/or networks operating in accordance with existingWireless-Gigabit-Alliance (WGA) and/or WirelessHD™ specifications and/orfuture versions and/or derivatives thereof, units and/or devices whichare part of the above networks, one way and/or two-way radiocommunication systems, cellular radio-telephone communication systems, acellular telephone, a wireless telephone, a Personal CommunicationSystems (PCS) device, a PDA device which incorporates a wirelesscommunication device, a mobile or portable Global Positioning System(GPS) device, a device which incorporates a GPS receiver or transceiveror chip, a device which incorporates an RFID element or chip, a MultipleInput Multiple Output (MIMO) transceiver or device, a Single InputMultiple Output (SIMO) transceiver or device, a Multiple Input SingleOutput (MISO) transceiver or device, a device having one or moreinternal antennas and/or external antennas, Digital Video Broadcast(DVB) devices or systems, multi-standard radio devices or systems, awired or wireless handheld device (e.g., BlackBerry, Palm Treo), aWireless Application Protocol (WAP) device, or the like.

Some embodiments may be used in conjunction with one or more types ofwireless communication signals and/or systems, for example, RadioFrequency (RF), Infra Red (IR), Frequency-Division Multiplexing (FDM),Orthogonal FDM (OFDM), Time-Division Multiplexing (TDM), Time-DivisionMultiple Access (TDMA), Extended TDMA (E-TDMA), General Packet RadioService (GPRS), extended GPRS, Code-Division Multiple Access (CDMA),Wideband CDMA (WCDMA), CDMA 2000, single-carrier CDMA, multi-carrierCDMA, Multi-Carrier Modulation (MDM), Discrete Multi-Tone (DMT),Bluetooth®, Global Positioning System (GPS), Wi-Fi, Wi-Max, ZigBee™,Ultra-Wideband (UWB), Global System for Mobile communication (GSM), 2 G,2.5 G, 3 G, 3.5 G, Enhanced Data rates for GSM Evolution (EDGE), or thelike. Other embodiments may be used in various other devices, systemsand/or networks.

The term “wireless device” as used herein includes, for example, adevice capable of wireless communication, a communication device capableof wireless communication, a communication station capable of wirelesscommunication, a portable or non-portable device capable of wirelesscommunication, or the like. In some demonstrative embodiments, awireless device may be or may include a peripheral that is integratedwith a computer, or a peripheral that is attached to a computer. In somedemonstrative embodiments, the term “wireless device” may optionallyinclude a wireless service.

Some demonstrative embodiments may be used in conjunction with suitablelimited-range or short-range wireless communication networks, forexample, a wireless area network, a “piconet”, a WPAN, a WVAN and thelike.

Reference is now made to FIG. 1, which schematically illustrates a blockdiagram of a system 100 in accordance with some demonstrativeembodiments.

In some demonstrative embodiments, one or more elements of system 100may be capable of communicating content, data, information and/orsignals over one or more suitable wireless communication links, forexample, a radio channel, an IR channel, a RF channel, a WirelessFidelity (WiFi) channel, and the like. One or more elements of system100 may optionally be capable of communicating over any suitable wiredcommunication links.

As shown in FIG. 1, in some demonstrative embodiments, system 100 mayinclude two or more devices, which communicate in a wireless manner totransfer data.

In some demonstrative embodiments, system 100 may include at least onewireless communication device (“station”), e.g., device 106 and/or 122,which may include a receiver 108 capable of receiving wirelesscommunications packets from one or more other devices of system 100.

In some demonstrative embodiments, wireless communication devices 106and/or 122 may include, for example, a PC, a desktop computer, a mobilecomputer, a laptop computer, a notebook computer, a tablet computer, aserver computer, a handheld computer, a handheld device, a PDA device, ahandheld PDA device, an on-board device, an off-board device, a hybriddevice (e.g., combining cellular phone functionalities with PDA devicefunctionalities), a consumer device, a vehicular device, a non-vehiculardevice, a mobile or portable device, a non-mobile or non-portabledevice, a cellular telephone, a PCS device, a PDA device whichincorporates a wireless communication device, a mobile or portable GPSdevice, a DVB device, a relatively small computing device, a non-desktopcomputer, a “Carry Small Live Large” (CSLL) device, an Ultra MobileDevice (UMD), an Ultra Mobile PC (UMPC), a Mobile Internet Device (MID),an “Origami” device or computing device, a device that supportsDynamically Composable Computing (DCC), a context-aware device, a videodevice, an audio device, an A/V device, a STB, a BD player, a BDrecorder, a DVD player, a HD DVD player, a DVD recorder, a HD DVDrecorder, a PVR, a broadcast HD receiver, a video source, an audiosource, a video sink, an audio sink, a stereo tuner, a broadcast radioreceiver, a flat panel display, a PMP, a DVC, a digital audio player, aspeaker, an audio receiver, a gaming device, an audio amplifier, a datasource, a data sink, a DSC, a media player, a Smartphone, a television,a music player, or the like.

In some demonstrative embodiments, devices 106 and/or 122 may include,for example, one or more of a processor 120, an input unit 112, anoutput unit 114, a memory unit 118, and a storage unit 116. Device 106may optionally include other suitable hardware components and/orsoftware components. In some demonstrative embodiments, some or all ofthe components of device 106 may be enclosed in a common housing orpackaging, and may be interconnected or operably associated using one ormore wired or wireless links. In other embodiments, components of device106 may be distributed among multiple or separate devices or locations.

Processor 120 includes, for example, a Central Processing Unit (CPU), aDigital Signal Processor (DSP), one or more processor cores, asingle-core processor, a dual-core processor, a multiple-core processor,a microprocessor, a host processor, a controller, a plurality ofprocessors or controllers, a chip, a microchip, one or more circuits,circuitry, a logic unit, an Integrated Circuit (IC), anApplication-Specific IC (ASIC), or any other suitable multi-purpose orspecific processor or controller. Processor 120 executes instructions,for example, of an Operating System (OS) of device 106, and/or of one ormore suitable applications.

Input unit 112 includes, for example, a keyboard, a keypad, a mouse, atouch-pad, a track-ball, a stylus, a microphone, or other suitablepointing device or input device. Output unit 114 includes, for example,a monitor, a screen, a flat panel display, a Cathode Ray Tube (CRT)display, a Liquid Crystal Display (LCD), an LED display, a plasmadisplay unit, one or more audio speakers or earphones, or other suitableoutput devices.

Memory unit 118 includes, for example, a Random Access Memory (RAM), aRead Only Memory (ROM), a Dynamic RAM (DRAM), a Synchronous DRAM(SD-RAM), a flash memory, a volatile memory, a non-volatile memory, acache memory, a buffer, a short term memory unit, a long term memoryunit, or other suitable memory units. Storage unit 116 includes, forexample, a hard disk drive, a floppy disk drive, a Compact Disk (CD)drive, a CD-ROM drive, a DVD drive, or other suitable removable ornon-removable storage units. Memory unit 118 and/or storage unit 116,for example, store data processed by device 106.

In some demonstrative embodiments, receiver 108 includes or may be partof, for example, one or more wireless transmitters, receivers and/ortransceivers able to send and/or receive wireless communication signals,RF signals, frames, blocks, transmission streams, packets, messages,specific data items, and/or any other type of communication data. Forexample, receiver 108 may include or may be implemented as part of asuitable wireless communication unit, for example, a suitable wirelessNetwork Interface Card (NIC), and the like.

Receiver 108 may include, or may be associated with, one or moreantennas or one or more sets of antennas 110. Antennas 110 may include,for example, an internal and/or external RF antenna, a dipole antenna, amonopole antenna, an omni-directional antenna, an end fed antenna, acircularly polarized antenna, a micro-strip antenna, a diversityantenna, or other type of antenna suitable for transmitting and/orreceiving wireless communication signals, blocks, frames, transmissionstreams, packets, messages and/or data.

In some demonstrative embodiments, receiver 108 may include any suitablePHY 134 and any suitable MAC 132 to process signals of wirelesscommunication packets received by receiver 108. Some wirelesscommunication packets may include relatively long packets, which maycontain a significant amount of information and/or data. Some packetsreceived by receiver 108 may be undesired packets and/or packets notintended to be received and/or processed by receiver 108, for example,unicast and/or multicast packets intended for other receivers. Completeprocessing of such undesired packets by PHY 134 may result in anunnecessary drainage of battery power of device 106.

In some demonstrative embodiments, communication device 106 may abortthe processing of a communication packet at the level of PHY 134, and asa result preserve battery power, e.g., as described in detail below.

In some demonstrative embodiments, receiver 108 may be capable ofprocessing a portion of a received communication packet, to determineaccording to the processed portion whether the communication packet isintended to be received by receiver 108 and, if the communication packetis not intended to be received by receiver 108, to abort processing of aremainder of the communication packet, e.g., of other portions of thepacket succeeding the processed portion, by one or more components ofPHY 134. For example, receiver 108 may determine that the packet is notintended to be received by receiver 108 based on the processed portionand prior to PHY 134 processing one or more of the other portions of thepacket, e.g., as described in detail below.

In some demonstrative embodiments, receiver 108 may abort the processingof the communication packet at the level of PHY 134 by powering down oneor more components of PHY 134, e.g., as described in detail below.Receiver 108 may later power up one or more of the components of PHY134, which were powered down (“the powered-down components”), e.g., inorder to receive signals of a successive packet. For example, receiver108 may determine a time at which the powered-down components are to bepowered up based on at least part of the processed portion of thepacket, e.g., as described in detail below.

Reference is now made to FIG. 2, which schematically illustrates asimplified block diagram of a wireless communication packet 200, inaccordance with some demonstrative embodiments.

In some demonstrative embodiments, wireless communication packet 200includes a leading portion 208 and a data portion 210.

In some demonstrative embodiments, leading portion 208 includes anysuitable information regarding the structure of packet 200 and/orregarding the data contained in data portion 210.

In some demonstrative embodiments, leading portion 208 may include oneor more headers, e.g., a first header 204, which may be a suitable PHYheader, for example, a PLCP header, and a second header 206, which maybe a suitable MAC header. In some demonstrative embodiments, leadingportion 208 may additionally or alternatively include a preamble (notshown in FIG. 2), for example, a PLCP preamble as shown and describedbelow with reference to FIG. 4A.

In some demonstrative embodiments, first header 204 and/or second header206 may include any suitable information regarding the structure ofpacket 200 and/or regarding the data contained in data portion 210. Forexample, first header 204 may include a suitable rate field 212, alength field 214 and/or any other suitable field; and/or second header206 may include a receiver address (RA) 216, a Basic Service SetIdentifier (BSSID) 218, a duration field 220 and/or any other suitablefield. Rate field 212 may include, for example, a data rate of dataportion 210, e.g., in terms of Mega bits per second (Mbps), for example,as described by the IEEE 802 standards and/or any other suitablestandard. Length field 214 may include a value representing a length,e.g., in bits and/or bytes, of data portion 210, for example, asdescribed by the IEEE 802 standards and/or any other suitable standard.RA 216 may include a suitable address of one or more destinationsintended to receive packet 200, e.g., an individual address or a groupaddress, for example, as described by the IEEE 802 standards and/or anyother suitable standard. BSSID 218 may include a value identifying aBasic Service Set (BSS), for example, as described by the IEEE 802standards and/or any other suitable standard. Duration field 220 mayinclude any suitable value representing a duration and/or length ofpacket 200, for example, as described by the IEEE 802 standards and/orany other suitable standard.

In some demonstrative embodiments, leading portion 208 may beimplemented in accordance with any structure known in the art. Forexample, first and second headers 204 and 206 of wireless communicationpacket 200 may be implemented as two separate parts of leading portion208, e.g., without any overlapping segments or fields, as showngenerally in FIG. 2, or they may be implemented as partially or fullyoverlapping parts of leading portion 208, e.g., with one or moreoverlapping fields or other segments of leading portion 208.

Referring back to FIG. 1, in accordance with some embodiments, receiver108 may receive signals of packet 200 (FIG. 2), and may process one ormore fields or other segments of leading portion 208 (FIG. 2), e.g.,headers 204 and/or 206 (FIG. 2), to determine whether or notcommunication packet 200 (FIG. 2) is intended to be received by receiver108, e.g., according to predetermined criteria applied to the one ormore processed fields or segments. If the communication packet is notintended to be received by receiver 108, receiver 108 may abortprocessing of a remainder of the communication packet 200 (FIG. 2) byPHY 134, e.g., by powering down PHY 134 for a period of timecorresponding to an anticipated length of the remainder of packet 200(FIG. 2).

In some demonstrative embodiments, first header 204 (FIG. 2) of packet200 (FIG. 2) is received and processed by PHY 134. PHY 134 may determinewhether packet 200 (FIG. 2) is intended to be received by receiver 108,e.g., based on information contained in first header 204 (FIG. 2). If,after processing first header 204 (FIG. 2), PHY 134 determines thatpacket 200 (FIG. 2) is not intended to be received by receiver 108, PHY134 may abort processing of the remainder of packet 200 (FIG. 2), forexample, by powering down at least one component of PHY 134, e.g., for aperiod of time corresponding to the anticipated length of the remainderof packet 200 (FIG. 2), e.g., as described in detail below.

In some demonstrative embodiments, if, after processing first header 204(FIG. 2), PHY 134 has not conclusively determined that packet 200 (FIG.2) is not intended to be received by receiver 108, PHY 134 may continueto process a second portion of packet 200 (FIG. 2), e.g., second header206 (FIG. 2), and transfer the second processed portion for furtherprocessing by MAC 132.

In some demonstrative embodiments, MAC 132 may determine whether or notpacket 200 (FIG. 2) is intended for receiver 108, e.g., based on one ormore fields of second header 206 (FIG. 2). MAC 132 may cause PHY 134 toabort processing of the remainder of packet 200 (FIG. 2), for example,if MAC 132 determines that packet 200 (FIG. 2) is not intended to bereceived by receiver 108, as explained in more detail below.

In some demonstrative embodiments, PHY 134 may include at least one RFreceiving portion 126 and at least one BB portion 128.

In some demonstrative embodiments, receiver 108 may include at least onecontroller 130 to controllably power down and/or power up one or morecomponents of PHY 134, e.g., one or more components of RF portion 126and/or BB portion 128, as described in detail below. Controller 130 maybe implemented by hardware and/or software and may include anycombination of separated or integrated elements. Although in theembodiments shown in FIG. 1, controller 130 may be implemented as partof PHY 134, in other embodiments, the functionality of controller 130may be incorporated into and/or performed by one or more suitablecomponents of PHY 134 and/or MAC 132.

In some demonstrative embodiments, RF portion 126 is capable ofreceiving, handling and/or processing signals of incoming packetsreceived via antennas 110. For example, RF portion 126 may include anysuitable Low Noise Amplifier (LNA), Band Pass Filter (BPF), Low PassFilter (LPF), Analog to Digital Convertor (A/D), and/or any othersuitable component. After receiving and processing a portion of packet200 (FIG. 2), RF portion 126 transfers the processed portion to BBportion 128 for further PHY processing.

In some demonstrative embodiments, BB portion 128 is capable ofreceiving the processed portion of packet 200 (FIG. 2) from RF portion126 and may include one or more processing units as are known in the artto further process the received portion of packet 200. For example, insome demonstrative embodiments, BB portion 128 may include a Timing andCarrier Recovery (TCR) module (not shown), a Fast Fourier Transform(FFT) module (not shown), an equalizer (not shown), a demodulator (notshown), a de-interleaver (not shown), a decoder 136, and/or adescrambler (not shown) and/or any other suitable component.

In some demonstrative embodiments, controller 130 may determine, e.g.,based on information contained in first header 204 (FIG. 2), whether ornot packet 200 (FIG. 2) is intended to be received by receiver 108. Forexample, first header 204 (FIG. 2) is received by device 106 via antenna110, and is processed by PHY 134. First header 204 (FIG. 2) may be firstprocessed by RF portion 126, then converted from analog to digitalformat, and transferred to BB portion 128. Controller 130 may receivefirst header 204 (FIG. 2) from BB portion 128, e.g., from decoder 136,as demonstrated, for example, by signal 111.

In some demonstrative embodiments, if controller 130 determines thatpacket 200 (FIG. 2) is not intended to be received by receiver 108,controller 130 may cause one or more elements of RF portion 126 and/orBB portion 128 to power down RF portion 126 and/or BB portion 128, thuscausing PHY 134 to abort further processing and/or decoding of packet200 (FIG. 2); and/or to later cause one or more elements of RF portion126 and/or BB portion 128 to power up, thus causing PHY 134 to resumeprocessing of a next incoming packet. For example, path 107 demonstratesat least one control signal utilized by controller 130 to power downand/or power up at least one component of RF portion 126, and path 109demonstrates at least one control signal utilized by controller 130 topower down and/or power up at least one component of BB portion 128.

In some demonstrative embodiments, controller 130 may utilize anysuitable switch, adjuster, dial, on/off toggle and/or any othermechanism to controllably power down and/or power up one or morecomponents of PHY 134 for example, RF portion 126 and/or BB portion 128and/or any sub-components thereof, and/or to controllably disable/enablethe activity of any timing mechanism of PHY 134, e.g., a clock.

In some demonstrative embodiments, controller 130 may determine whetheror not packet 200 (FIG. 2) is intended to be received by receiver 108based on rate field 212 (FIG. 2) and/or length filed 214 (FIG. 2). Forexample, controller 130 may determine that packet 200 (FIG. 2) is notintended to be received by receiver 108 if rate field 212 (FIG. 2)includes a rate, which is not supported by receiver 108. In one example,controller 130 may determine that packet 200 (FIG. 2) is not intended tobe received by receiver 108 if rate field 212 indicates a data rate,e.g., 5.5 Mbps, which is not supported by receiver 108, e.g., ifreceiver 108 supports data rates of 11 Mbps.

In some demonstrative embodiments, PHY 134 may process a second portionof packet 200 (FIG. 2), for example, second header 206 (FIG. 2), andpass the second portion for further processing by additional componentsof receiver 106, for example, by MAC 132, e.g., if controller 130 isunable to determine that packet 200 (FIG. 2) is not intended to bereceived by receiver 108.

In some demonstrative embodiments, MAC 132 may determine whether or notpacket 200 (FIG. 2) is intended to be received by receiver 108 byconsidering one or more elements included in second header 206 (FIG. 2).For example, MAC 132 may process and/or check at least one of RA 216(FIG. 2), BSSID 218 (FIG. 2) and/or any other suitable field or value ofsecond header 206 (FIG. 2).

In some demonstrative embodiments, MAC 132 may include any suitablelower MAC layer 138 and any suitable upper MAC layer 140. For example,lower MAC layer 138 may be implemented in micro-code (“uCode”), andupper MAC layer 140 may be implemented as part of a suitable driver ofdevice 106.

In some demonstrative embodiments, lower MAC layer 138 may determine,based on second header 206 (FIG. 2) whether or not packet 200 (FIG. 2)is intended to be received by receiver 108. Lower MAC layer 138 mayprovide at least one feedback signal 113 to controller 130, e.g.,indicating to controller 130 that packet 200 (FIG. 2) is not intended tobe received by receiver 108.

In some demonstrative embodiments, lower MAC layer 138 may compare, forexample, RA 216 (FIG. 2) to a MAC address of receiver 108. Lower MAClayer 138 may determine that packet 200 (FIG. 2) is not intended to bereceived by receiver 108 and send feedback signal 113 to controller 130causing controller 130 to power down at least one component of PHY 134and thus abort further processing of the remainder of packet 200 (FIG.2), e.g., if RA 216 does not match the MAC address of receiver 108.

Additionally or alternatively, in some demonstrative embodiments, lowerMAC layer 138 may check if RA 216 includes a broadcast address and, ifso, lower MAC layer 138 may check BSSID 218 (FIG. 2). Lower MAC layer138 may determine that packet 200 (FIG. 2) is not intended to bereceived by receiver 108 and send feedback signal 113 to controller 130causing controller 130 to power down at least one component of PHY 134and thus abort further processing of the remainder of packet 200 (FIG.2), e.g., if BSSID 218 (FIG. 2) does not indicate a BSS, which includesand/or is associated with device 106.

Additionally or alternatively, in some demonstrative embodiments, lowerMAC layer 138 may check if RA 216 is a multi-cast address and, if so,lower MAC layer 138 may check whether RA 216 includes a multicastaddress of a multicast group including receiver 108. Lower MAC layer 138may determine that packet 200 (FIG. 2) is not intended to be received byreceiver 108 and send feedback signal 113 to controller 130 causingcontroller 130 to power down at least one component of PHY 134 and thusabort further processing of the remainder of packet 200 (FIG. 2), e.g.,if RA 216 includes a multicast address which does not include receiver108, e.g., if BSSID 218 (FIG. 2) indicates a BSS, which does not includeand/or is associated with device 106.

Additionally or alternatively, in some demonstrative embodiments, lowerMAC layer 138 may determine that the processing of packet 200 (FIG. 2)is not to be aborted, e.g., thereby allowing PHY 134 to process theentire packet 200 (FIG. 2), if one or more predefined criteria are met.For example, lower MAC layer 138 may determine that the processing ofpacket 200 (FIG. 2) is not to be aborted if RA 216 (FIG. 2) matches theMAC address of receiver 108; if RA 216 (FIG. 2) is a broadcast addressand BSSID 218 (FIG. 2) indicates a BSS, which includes and/or isassociated with device 106; if RA 216 (FIG. 2) is a multicast address ofa multicast group including receiver 108; if packet 200 (FIG. 2)includes a control frame, for example, as a Request to Send (RTS) frame,a Clear to Send (CTS) frame and/or Acknowledgement (ACK) frame, e.g., asdescribed by the 802 standard and/or any other suitable standard; and/orif a parser (not shown) of lower MAC 138 is bypassed, e.g., whenoperating in a promiscuous mode.

It is noted, that MAC 132 may not be able to determine whether or notone or more portions of header 206 are corrupt. For example, RA 216(FIG. 2) may be corrupt, e.g., including an erroneous RA, and MAC 132may not be able to detect the corrupt RA 216 (FIG. 2). In such asituation, MAC 132 may determine whether or not packet 200 (FIG. 2) isintended to be received by receiver 108 based on the corrupt RA.

In one case, the corrupt RA may include an RA indicating that packet 200(FIG. 2) is intended for receiver 108, e.g., although the actual,uncorrupt, RA may have indicated that packet 200 (FIG. 2) is notintended for receiver 108. This case, may have a relatively lowlikelihood, for example, a likelihood of 1−(2⁴⁸−1)/2⁴⁸, assuming a48-bit RA. In this case, receiver 108 may determine, based on header 206(FIG. 2) that packet 200 (FIG. 2) is intended to be received by receiver108, e.g., although packet 200 (FIG. 2) may actually not be intended tobe received by receiver 108. As a result, receiver 108 may not abortprocessing the remainder of packet 200 (FIG. 2) by PHY 134, and packet200 (FIG. 2) may “dropped” later, e.g., based on any suitable check,e.g., a frame check sequence (FCS).

In a second case, the corrupt RA may include an RA indicating thatpacket 200 (FIG. 2) is not intended for receiver 108, e.g., although theactual, uncorrupt, RA may have indicated that packet 200 (FIG. 2) isintended for receiver 108. In this case, receiver 108 may abortprocessing the remainder of packet 200 (FIG. 2) by PHY 134.

In some demonstrative embodiments, controller 130 may controllably powerdown one or more components of PHY 134, e.g., one or more components ofRF portion 126 and/or BB portion 128, based on signals 111 and/or 113,for example, such that PHY 134 aborts processing of one or moreremaining unprocessed portions of packet 200 (FIG. 2), for a power-downperiod. For example, if signals 111 and/or 113 indicate that packet 200(FIG. 2) is not intended to be received by receiver 108, then controller130 may controllably power down one or more components of PHY 134, e.g.,one or more components of RF portion 126 and/or BB portion 128, suchthat PHY 134 aborts processing of header 206 (FIG. 2) and data portion210 (FIG. 2). If signal 111 do not indicate that packet 200 (FIG. 2) isnot intended to be received by receiver 108, while signal 113 doindicate that packet 200 (FIG. 2) is not intended to be received byreceiver 108, then controller 130 may controllably power down one ormore components of PHY 134, e.g., one or more components of RF portion126 and/or BB portion 128, such that PHY 134 aborts processing of dataportion 210 (FIG. 2).

In some demonstrative embodiments, receiver 108 may determine the powerdown period based on an anticipated remaining transmit time (TxTime) ofpacket 200 (FIG. 2). The precise calculation of the power down timeperiod may enable the precise abortion of redundant packet processing byPHY 134 without or with minimal affect on the reception and processingof future packets.

In some demonstrative embodiments, controller 130 may calculate thepower down period based on information included in the processed firstheader 204 (FIG. 2), for example, based on rate field 212 (FIG. 2)and/or length field 214 (FIG. 2), which may relate to a Physical layerService Data Unit (PSDU) of packet 200 (FIG. 2). In one example, ifpacket 200 (FIG. 2) includes an aggregate MAC service data unit(A-MSDU), then the PSDU may include header 206 and an A-MSDU. In anotherexample, if packet 200 (FIG. 2) includes an aggregate MAC protocol dataunit (A-MPDU), then the PSDU may include a collection of one or more MACprotocol data units (MPDUs). In other embodiments, packet 200 mayinclude any other suitable packet and/or format.

In some demonstrative embodiments, controller 130 may determine thepower down period to correspond to an anticipated remaining duration ofa remainder of packet 200 (FIG. 2), e.g., upon receiving signals 111and/or 113 indicating that packet 200 (FIG. 2) is not intended to bereceived by receiver 108. For example, controller 130 may determine thepower down period based on the duration of packet 200 (FIG. 2) and anelapsed time period since initial detection of packet 200 (FIG. 2) byreceiver 108. For example, controller 130 may count the elapsed timesince receiving packet 200 (FIG. 2).

In some demonstrative embodiments, controller 130 may determine thepower down period based on duration field 220 (FIG. 2), e.g., if thetransmission of packet 200 (FIG. 2) does not implement TransmitOpportunity (TxOP) termination. For example, MAC 132 may provide thevalue of duration field 220 (FIG. 2), e.g., as part of and/or togetherwith signals 113. However, if header 206 is corrupt, e.g., as describedabove, then determining the power down period based on duration field220 (FIG. 2) may result in an erroneous power down period.

In some demonstrative embodiments, header 206 (FIG. 2) may also includea check field 221 (FIG. 2), e.g., a Cyclic Redundancy Check (CRC) field,including a value, which enables detecting and error and/or corruptionof header 206. According to these embodiments, upon receiving header 206(FIG. 2), MAC 132 may determine whether or not header 206 (FIG. 2) iscorrupt, e.g., based on check field 221 (FIG. 2). MAC 132 may extractduration field 220 (FIG. 2) from header 206 (FIG. 2) and provide MACduration value of duration field 220 (FIG. 2) to controller 130, e.g.,via signals 113, for example, if MAC 132 can determine that header 206(FIG. 2) is not corrupt. According to these embodiments, the MACduration value of duration field 220 (FIG. 2) may indicate a remainingTxOP duration after packet 200 (FIG. 2) is received. Controller 130 maydetermine the power down period, for example, by combining the MACduration value and the anticipated remaining duration of packet 200(FIG. 2). For example, controller 130 may determine the power downperiod to be equal to a sum of the MAC duration value and theanticipated remaining duration of packet 200 (FIG. 2).

In some embodiments, controller 130 may determine the power down periodbased on information other than duration field 220 (FIG. 2), forexample, one or more other elements of header 204 and/or header 206,e.g., as described herein. For example, if the transmission of packet200 (FIG. 2) does implement TxOP termination then and controller 130determines the power down period based on duration field 220 (FIG. 2),then receiver 108 may not be able to receive an indication, e.g., asuitable Contention-Free end (CF-end) frame, that the TxOP is to beterminated, prior to the end of the TxOP indicated corresponding toduration field 220 (FIG. 2).

In some demonstrative embodiments, controller 130 may controllably powerup the powered down components, e.g., prior to and/or at then end of thepower down period, such that PHY 134 may process signals of a successivepacket, as described in detail below.

In some demonstrative embodiments, powering up some components of PHY134, e.g., digital components of BB portion 128, may be responsiverelatively immediately. Accordingly, controller 130 may power up these“immediate response” components substantially at the end of the durationof packet 200 (FIG. 2). However, powering down and/or powering up ofother components of PHY 134, especially components of RF portion 126,may not be immediately responsive, due to the nature of powering down/upof certain components, e.g., analog components of RF portion 126. Forexample, such “delayed response” components may require a power-up timeperiod for powering up. Accordingly, receiver 108 may be capable ofdetermining the power down period of time prior to initiating the powerup of the delayed-response components, based on a combination of theduration of packet 200 (FIG. 2) and the power-up period, e.g., asdescribed below. For example, controller 130 may initiate the poweringup of the delayed response components prior to the end of the durationof packet 200 (FIG. 2), e.g., at least the power-up period, prior to theend of the duration of packet 200 (FIG. 2), such that thedelayed-response components may be powered up when the duration ofpacket 200 (FIG. 2) has ended. For example, controller 130 may generatesignals 107 and 109 to power down components of RF portion 126 and BBportion 128, e.g., substantially simultaneously; while controller 130may generate signals 107 to power up components of RF portion 126 at afirst time, e.g., the power-up period prior to the end of the durationof packet 200 (FIG. 2), and to generate signals 109 to power upcomponents of BB portion 128 at a second, later, time, e.g., at the endof the duration of packet 200 (FIG. 2).

Reference is now made to FIG. 3, which schematically illustrates amethod of selectively aborting reception of wireless communicationpackets, in accordance with some demonstrative embodiments. In somedemonstrative embodiments, one or more of the operations of the methodof FIG. 3 may be performed by a wireless communication device, forexample, wireless communication device 106 (FIG. 1), a receiver, e.g.,receiver 108 (FIG. 1) and/or any other wireless communication devicecapable of receiving wireless communication packets.

As indicated in block 304, the method may include receiving a portion ofa packet by a receiver. For example, receiver 108 (FIG. 1) may receivesignals of at least part of leading portion 208 (FIG. 2) of packet 200(FIG. 2), e.g., as described above.

As indicated in block 306, the method may include selectively abortingprocessing of a remainder of the packet by a PHY of the receiver, basedon the processed portion. For example, based on header 204 (FIG. 2)and/or header 206 (FIG. 2), receiver 108 (FIG. 1) may selectively abortprocessing of remaining portions of packet 200 (FIG. 2) by PHY 134 (FIG.1), e.g., as described above.

As indicated in block 308, the method may include processing a firstheader of the packet. As indicated at block 309, processing the firstheader may include processing a PHY header by the PHY. For example, PHY134 (FIG. 1) may process header 204 (FIG. 2), e.g., as described above.

As indicated in block 310, the method may include determining whetherthe packet is intended to be received by the receiver based on the firstheader. For example, controller 130 (FIG. 1) may determine whether ornot packet 200 (FIG. 2) is to be received by receiver 108 (FIG. 1) basedon signal 111 (FIG. 1), e.g., as described above.

As indicated in block 312, the method may include processing a secondheader of the packet, e.g., if it cannot be determined, based on thefirst header, that the packet is not intended to be received by thereceiver. As indicated in block 313, processing the second header mayinclude processing a MAC header by a MAC of the receiver. For example,MAC 134 (FIG. 1) may process header 206 (FIG. 2), e.g., after beinginitially processed by PHY 132 (FIG. 1), as described above.

As indicated in block 314, the method may include determining whether ornot the packet is intended to be received by the receiver based on thesecond header. For example, MAC 132 (FIG. 1) may determine whether ornot packet 200 (FIG. 2) is intended to be received by receiver 108 (FIG.1), e.g., based on header 206, as described above.

As indicated in block 316, the method may include processing otherremaining portions of the packet, e.g., if criteria to abort processingof the packet are not met. For example, if it has not been determined,as explained above, by either PHY 134 (FIG. 1) or MAC 132 (FIG. 1), thatpacket 200 (FIG. 2) is not intended for reception by receiver 108 (FIG.1), then the remaining portions of packet 200 (FIG. 2), which have notbeen processed, may continue to be received and processed by PHY 134(FIG. 1) and MAC 132 (FIG. 1).

As indicated in block 317, the method may include determining a powerdown period of time, for example, if it is determined, e.g., based onthe first and/or second headers, that the packet is not intended to bereceived by the receiver. The power down period may be determined, forexample, based on the received portion of the packet, e.g., as describedbelow.

As indicated in block 324, determining the power down period may includedetermining the power down period based on a PLCP header. For example,controller 130 (FIG. 1) may determine the power down period based onheader 204 (FIG. 2), e.g., as described above.

As indicated in block 326, the method may include determining whether ornot TxOP termination is implemented. For example, a device of system 100(FIG. 1), for example, an AP, e.g., which may be implemented as part ofdevice 122 (FIG. 1) and/or any other device, may use suitable signals,e.g., frames and/or packets, to indicate to device 106 whether or notTxOP may be implemented. In one example, the AP may transmit a beaconincluding a suitable indication, e.g., a bit having a predefined value,to indicate that a wireless communication device receiving the beacon isnot to implement TxOP termination.

As indicated in block 328, determining the power down period may includedetermining the power down period based on a MAC duration field in thesecond header, e.g., if TXOP termination is not implemented. Forexample, controller 130 (FIG. 1) may determine the power down periodbased on duration field 220 (FIG. 1), e.g., as described above.

As indicated in block 320, the method may include powering down at leastone component of the PHY, for the power down period. For example,controller 130 (FIG. 1) may power down one or more components of PHY 134(FIG. 1) for the power down period, e.g., as described above.

As indicated at block 318, powering down the one or more components mayinclude powering down one or more RF components. For example, controller130 (FIG. 1) may power down one or more components of RF portion 126(FIG. 1) for the power down period, e.g., as described above.

As indicated at block 322, powering down the one or more components mayinclude powering down one or more BB components. For example, controller130 (FIG. 1) may power down one or more components of BB portion 128(FIG. 1) for the power down period, e.g., as described above.

As indicated at block 323, the method may include powering up one ormore of the components, which were powered down. For example, controller130 (FIG. 1) may power up one or more of the components of BB portion128 (FIG. 1) and/or RF portion 126 (FIG. 1), for example, prior toand/or at the end of the power down period, e.g., as described above.

Reference is now made to FIGS. 4 a and 4 b, which schematicallyillustrate block diagrams of two exemplary types of packets to bereceived, in accordance with some demonstrative embodiments. Any othersuitable packets and/or packet formats may be received and/or processedin accordance with other embodiments.

FIG. 4 a illustrates a demonstrative frame format of a Physical PacketData Unit (PPDU) 400, e.g., in accordance with the IEEE 802.11 standard.PPDU 400 may include a PLCP preamble 404, a first header 406, forexample, a PLCP header, a second header 408, for example, a MAC header,a frame body 410, e.g., including data, and a FCS field 412.

In some demonstrative embodiments, header 406 may include rate field 212(FIG. 2) representing a data rate of PPDU 400, and length field 214(FIG. 2) specifying a length of a MPDU of PPDU 400.

According to these embodiments, PHY 134 (FIG. 1) may process header 406to determine, e.g., based on the rate field, whether or not PPDU 400 isintended to be received by receiver 108 (FIG. 1), e.g., as describedabove. Controller 130 (FIG. 1) may power down one or more components ofPHY 134 (FIG. 1), e.g., upon determining that PPDU 400 is not intendedto be received by receiver 108 (FIG. 1). PHY 134 (FIG. 1) may continueto process header 408 and provide the processed header 408 to MAC 132(FIG. 1), e.g., if PHY 134 (FIG. 1) cannot determine that PPDU 400 isnot intended to be received by receiver 108 (FIG. 1). Lower MAC layer138 (FIG. 1) may determine whether or not PPDU 400 is intended to bereceived by receiver 108 (FIG. 1), e.g., based on header 408. Lower Maclayer 138 (FIG. 1) may cause controller 130 (FIG. 1) to power down oneor more components of PHY 134 (FIG. 1), e.g., upon determining that PPDU400 is not intended to be received by receiver 108 (FIG. 1). PHY 134(FIG. 1) and MAC 132 (FIG. 1) may continue to process other portions ofPPDU 400, e.g., if lower MAC layer 138 (FIG. 1) cannot determine thatPPDU 400 is not intended to be received by receiver 108 (FIG. 1).

FIG. 4 b illustrates a demonstrative frame format of an A-MPDU 402,e.g., in accordance with the IEEE 802.11n standard. A-MPDU 402 mayinclude a first header 403, e.g., a PLCP header, followed by one or moreA-MPDU subframes 415. A-MPDU subframe 415 may include a length field414, a length CRC field 417, a delimiter signature 416, a MPDU 418, andan FCS 412, optionally followed by one or more padding bits 420. Lengthfield 414 may specify a length of MPDU 418, and CRC field may include avalue for checking length field 414. MPDU 418 may include a MAC header419, e.g., analogous to MAC header 206 (FIG. 2).

According to these embodiments, PHY 134 (FIG. 1) may process header 403to determine, e.g., based on the rate field, whether or not A-MPDU 402is intended to be received by receiver 108 (FIG. 1), e.g., as describedabove. Controller 130 (FIG. 1) may power down one or more components ofPHY 134 (FIG. 1), e.g., upon determining that A-MPDU 402 is not intendedto be received by receiver 108 (FIG. 1). PHY 134 (FIG. 1) may determinethe duration of A-MPDU 402 based on PLCP header 403. PHY 134 (FIG. 1)may then process a MAC header 419 of a first MPDU 418 of A-MPDU 402 andprovide the processed MAC header 419 to MAC 132 (FIG. 1). MAC 132(FIG. 1) may determine whether or not A-MPDU 402 is intended to bereceived by receiver 108 (FIG. 1), e.g., based on header 419, forexample, while PHY 134 (FIG. 1) processes a remainder of MPDU 418. MAC132 (FIG. 1) may cause controller 130 (FIG. 1) to power down one or morecomponents of PHY 134 (FIG. 1), e.g., upon determining that A-MPDU 402is not intended to be received by receiver 108 (FIG. 1). Controller 130(FIG. 1) may power down the one or more components of PHY 134 (FIG. 1)for the entire duration of A-MPDU 402, based on the determination of MAC132 with respect to first MPDU 418, e.g., since all MPDUs 418 of A-MPDU402 may have the same RA. PHY 134 (FIG. 1) and MAC 132 (FIG. 1) maycontinue to process other portions of A-MPDU 402, e.g., if MAC 132(FIG. 1) cannot determine that A-MPDU 402 is not intended to be receivedby receiver 108 (FIG. 1). In one example, A-MPDU 402 may have a lengthof 32 Kilobytes, and header 403 may have a length of less than 50 bytes.Accordingly, components of PHY 134 (FIG. 1) may be powered down foralmost the entire duration of A-MPDU 402, e.g., for more than 90% of theduration of A-MPDU 402, if, for example, PHY 134 (FIG. 1) determinesthat A-MPDU 402 is not intended to be received by receiver 108 (FIG. 1)based on header 403.

Reference is made to FIG. 5, which schematically illustrates an articleof manufacture 400, in accordance with some demonstrative embodiments.Article 500 may include a machine-readable storage medium 502 to storelogic 504, which may be used, for example, to perform at least part ofthe functionality of receiver 108 (FIG. 1) and/or wireless communicationdevice 106 (FIG. 1); and/or to perform one or more operations of themethod of FIG. 3.

In some demonstrative embodiments, article 500 and/or machine-readablestorage medium 502 may include one or more types of computer-readablestorage media capable of storing data, including volatile memory,non-volatile memory, removable or non-removable memory, erasable ornon-erasable memory, writeable or re-writeable memory, and the like. Forexample, machine-readable storage medium 502 may include, RAM, DRAM,Double-Data-Rate DRAM (DDR-DRAM), SDRAM, static RAM (SRAM), ROM,programmable ROM (PROM), erasable programmable ROM (EPROM), electricallyerasable programmable ROM (EEPROM), Compact Disk ROM (CD-ROM), CompactDisk Recordable (CD-R), Compact Disk Rewriteable (CD-RW), flash memory(e.g., NOR or NAND flash memory), content addressable memory (CAM),polymer memory, phase-change memory, ferroelectric memory,silicon-oxide-nitride-oxide-silicon (SONOS) memory, a disk, a floppydisk, a hard drive, an optical disk, a magnetic disk, a card, a magneticcard, an optical card, a tape, a cassette, and the like. Thecomputer-readable storage media may include any suitable media involvedwith downloading or transferring a computer program from a remotecomputer to a requesting computer carried by data signals embodied in acarrier wave or other propagation medium through a communication link,e.g., a modem, radio or network connection.

In some demonstrative embodiments, logic 504 may include instructions,data, and/or code, which, if executed by a machine, may cause themachine to perform a method, process and/or operations as describedherein. The machine may include, for example, any suitable processingplatform, computing platform, computing device, processing device,computing system, processing system, computer, processor, or the like,and may be implemented using any suitable combination of hardware,software, firmware, and the like.

In some demonstrative embodiments, logic 504 may include, or may beimplemented as, software, a software module, an application, a program,a subroutine, instructions, an instruction set, computing code, words,values, symbols, and the like. The instructions may include any suitabletype of code, such as source code, compiled code, interpreted code,executable code, static code, dynamic code, and the like. Theinstructions may be implemented according to a predefined computerlanguage, manner or syntax, for instructing a processor to perform acertain function. The instructions may be implemented using any suitablehigh-level, low-level, object-oriented, visual, compiled and/orinterpreted programming language, such as C, C++, Java, BASIC, Matlab,Pascal, Visual BASIC, assembly language, machine code, and the like.

Functions, operations, components and/or features described herein withreference to one or more embodiments, may be combined with, or may beutilized in combination with, one or more other functions, operations,components and/or features described herein with reference to one ormore other embodiments, or vice versa.

While certain features of the invention have been illustrated anddescribed herein, many modifications, substitutions, changes, andequivalents may occur to those skilled in the art. It is, therefore, tobe understood that the appended claims are intended to cover all suchmodifications and changes as fall within the true spirit of theinvention.

What is claimed is:
 1. A wireless communication device comprising: areceiver including a Physical Layer (PHY) and a Media Access Control(MAC) layer to process signals of a wireless communication packet, thepacket including an aggregate MAC protocol data unit (A-MPDU) includinga PHY header to be processed by the PHY, the PHY header followed by aplurality of subframes, each subframe including a MAC header to beprocessed by the MAC layer, wherein the physical layer is to at leastpartially process a portion of the PHY header prior to the plurality ofsubframes, to determine based on the portion of the PHY header, whetherthe packet is intended to be received by the receiver and, if the packetis not intended to be received by the receiver, to abort processing of aremainder of the communication packet by one or more components of thePHY, wherein, if processing is not to be aborted based on the portion ofthe PHY header, the MAC layer is to process a first subframe of saidA-MPDU, while the PHY is to process at least one subframe subsequent tosaid first subframe, wherein said MAC layer is to determine based on aMAC header of said first subframe whether the packet is intended to bereceived by the receiver and, if the packet is not intended to bereceived by the receiver, to cause the PHY to abort processing of thewireless communication packet, and wherein the receiver is to determinea power-down period based on a Physical Layer Convergence Procedure(PLCP) header when Transmit Opportunity (TxOp) termination isimplemented, or based on a duration field of the MAC header of the firstsubframe when TxOp termination is not implemented, and to power down oneor more receiver components for the power-down period.
 2. The device ofclaim 1, wherein the physical layer is to determine whether the packetis intended to be received by the receiver based on the PLCP header. 3.The device of claim 1, wherein the receiver is to abort processing ofthe wireless communication packet by powering down at least onecomponent of the physical layer.
 4. The device of claim 3, wherein thereceiver is to power-up the at least one component after the power-downperiod.
 5. The device of claim 4, wherein the at least one componentincludes at least one radio-frequency (RF) component having a power-updelay period for powering up the RF component, and wherein the receiveris to determine the power-down time period based on the power-up delayperiod.
 6. The device of claim 1, wherein the one or more componentsinclude at least one radio-frequency (RF) component of the physicallayer.
 7. The device of claim 1, wherein the one or more componentsinclude at least one baseband (BB) component of the physical layer.
 8. Amethod comprising: at least partially processing a portion of a Physicallayer (PHY) header of a wireless communication packet, to determinebased on the portion of the PHY header, whether the packet is intendedto be received by a receiver, wherein the wireless communication packetincludes an aggregate MAC protocol data unit (A-MPDU) including the PHYheader followed by a plurality of subframes, each subframe including aMAC header; if the packet is not intended to be received by thereceiver, aborting processing of a remainder of the packet, includingthe plurality of subframes of the packet, by one or more components ofthe receiver; and if processing is not aborted based on the portion ofthe PHY header, processing a first subframe of said A-MPDU by a MAClayer, while processing at least one subframe subsequent to said firstsubframe by a PHY, determining based on a MAC header of said firstsubframe whether the packet is intended to be received by the receiverand, if the packet is not intended to be received by the receiver,aborting processing of the wireless communication packet, whereinaborting processing of the wireless communication packet comprisesdetermining a power-down period based on a Physical Layer ConvergenceProcedure (PLCP) header when Transmit Opportunity (TxOp) termination isimplemented, or based on a duration field of the MAC header of the firstsubframe when TxOp termination is not implemented, and powering down oneor more receiver components for the power-down period.
 9. The method ofclaim 8, wherein aborting processing of the remainder of said packetincludes powering down at least one component of the physical layer. 10.The method of claim 9 including powering-up the at least one componentafter the power-down period.
 11. The method of claim 10, wherein the atleast one component includes at least one radio-frequency (RF) componenthaving a power-up delay period for powering up the RF component, andwherein determining the power-down period includes determining thepower-down period based on the power-up delay period.
 12. The method ofclaim 8, wherein the one or more components include at least oneradio-frequency (RF) component of the physical layer.
 13. A systemcomprising: at least one wireless communication device including: atleast one antenna to receive signals of a wireless communication packetincluding an aggregate Media Access Control (MAC) protocol data unit(A-MPDU), the A-MPDU including a Physical Layer (PHY) header followed bya plurality of subframes, each subframe including a MAC header; areceiver including a PHY and a MAC layer, the PHY to at least partiallyprocess a portion of the PHY header, wherein, prior to processing of theplurality of subframes by said receiver, said PHY is to determine basedon the portion of the PHY header whether the packet is intended to bereceived by the receiver and, if the packet is not intended to bereceived by the receiver, to abort processing of a remainder of thepacket by one or more components of the PHY, wherein, if processing isnot to be aborted based on the portion of the PHY header, the MAC layeris to process a first subframe of said A-MPDU, while the PHY is toprocess at least one subframe subsequent to said first subframe, whereinsaid MAC layer is to determine based on a MAC header of said firstsubframe whether the packet is intended to be received by the receiverand, if the packet is not intended to be received by the receiver, tocause the PHY to abort processing of the wireless communication packet,and wherein the receiver is to determine a power-down period based on aPhysical Layer Convergence Procedure (PLCP) header when TransmitOpportunity (TxOp) termination is implemented, or based on a durationfield of the MAC header of the first subframe when TxOp termination isnot implemented, and to power down one or more receiver components forthe power-down period.
 14. The system of claim 13, wherein the receiveris to abort processing of the remainder of said packet by powering downat least one component of the physical layer.
 15. A product including astorage having stored thereon instructions, wherein the instructions,when executed by a machine, cause the machine to: at least partiallyprocess, by a Physical layer (PHY) of a receiver, a portion of a PHYheader of a wireless communication packet, to determine based on theportion of the PHY header whether the packet is intended to be receivedby the receiver, wherein the wireless communication packet includes anaggregate Media Access Control (MAC) protocol data unit (A-MPDU)including the PHY header followed by a plurality of subframes, eachsubframe including a MAC header; if the packet is not intended to bereceived by the receiver, to abort processing of a remainder of thepacket by one or more components of the PHY of the receiver; and ifprocessing is not aborted based on the portion of the PHY header, toprocess a first subframe of said A-MPDU by a MAC layer, while processingat least one subframe subsequent to said first subframe by the PHY, todetermine based on a MAC header of said first subframe whether thepacket is intended to be received by the receiver, and, if the packet isnot intended to be received by the receiver, to abort processing of thewireless communication packet by determining a power-down period basedon a Physical Layer Convergence Procedure (PLCP) header when TransmitOpportunity (TxOp) termination is implemented, or based on a durationfield of the MAC header of the first subframe when TxOp termination isnot implemented, and powering down one or more receiver components forthe power-down period.
 16. The product of claim 15, wherein theinstructions resulting in aborting processing of the remainder of saidpacket include instructions resulting in powering down at least onecomponent of the physical layer.
 17. The product of claim 15, whereinthe instructions result in determining by the PHY whether the packet isintended to be received based on at least one predefined field of thePHY header.
 18. A wireless communication device comprising: a receiverincluding a physical layer (PHY) and a medium access control layer(MAC), the receiver to receive Orthogonal Frequency Division-Multiplexed(OFDM) signals of a wireless communication packet including an aggregateMAC protocol data unit (A-MPDU), the A-MPDU including a PHY headerfollowed by a plurality of subframes, each subframe including a MACheader, the receiver to at least partially process by the PHY at leastone predefined field of the PHY header of the packet prior to processingof the plurality of subframes, and to determine based on the fieldwhether the packet is intended to be received by the receiver and, ifthe packet is not intended to be received by the receiver, to abortprocessing of a remainder of the packet by one or more components of thePHY layer, wherein, if processing is not to be aborted based on thefield of the PHY header, the MAC layer is to process a first subframe ofsaid A-MPDU, while the PHY is to process at least one subframesubsequent to said first subframe, wherein said MAC layer is todetermine based on a MAC header of said first subframe whether thepacket is intended to be received by the receiver and, if the packet isnot intended to be received by the receiver, to cause the PHY to abortprocessing of the wireless communication packet, wherein the receiver isto determine a power-down period based on a Physical Layer ConvergenceProcedure (PLCP) header when Transmit Opportunity (TxOp) termination isimplemented, or based on a duration field of the MAC header of the firstsubframe when TxOp termination is not implemented, and to power down oneor more receiver components for the power-down period; a centralprocessing unit (CPU); a memory unit; and a Bluetooth (BT) system. 19.The device of claim 18, further including a Global Positioning System(GPS).
 20. The device of claim 18, wherein: the MAC layer includes alower MAC layer.
 21. The device of claim 18, wherein the memory unitincludes a Read-Only-Memory (ROM).
 22. The device of claim 18, whereinthe receiver and the BT system are configured to be used in conjunctionwith one another.
 23. The device of claim 18, further comprising aninput unit and an output unit.
 24. The device of claim 18, wherein theBT system, the PHY layer, the MAC layer, the CPU, and the memory unitare enclosed in a common packaging.
 25. The device of claim 24, whereinthe device includes a smartphone, a tablet or a router.
 26. The deviceof claim 18, wherein the physical layer is to determine whether thepacket is intended to be received by the receiver based on the PLCPheader.
 27. The device of claim 18, wherein the receiver is to abortprocessing of the remainder of said packet by powering down at least onecomponent of the physical layer.
 28. The device of claim 27, wherein thereceiver is to power-up the at least one component after the power-downperiod.
 29. The device of claim 28, wherein the at least one componentincludes at least one radio-frequency (RF) component having a power-updelay period for powering up the RF component, and wherein the receiveris to determine the power-down period based on the power-up delayperiod.
 30. The device of claim 18, wherein the one or more componentsinclude at least one radio-frequency (RF) component of the physicallayer.
 31. The device of claim 18, wherein the one or more componentsinclude at least one baseband (BB) component of the physical layer. 32.A wireless communication device comprising: a receiver including aphysical layer (PHY) and a medium access control layer (MAC), the MAClayer including a lower MAC layer, the receiver to receive OrthogonalFrequency Division-Multiplexed (OFDM) signals of a wirelesscommunication packet including an aggregate MAC protocol data unit(A-MPDU), the A-MPDU including a PHY header followed by a plurality ofsubframes, each subframe including a MAC header, the receiver to atleast partially process by the PHY a predefined field of a PHY header ofthe packet, and to determine based on the field of the PHY headerwhether the packet is intended to be received by the receiver and, ifthe packet is not intended to be received by the receiver, to abortprocessing of a remainder of the packet, wherein, if processing is notto be aborted based on the field of the PHY header, the MAC layer is toprocess a first subframe of said A-MPDU, while the PHY is to process atleast one subframe subsequent to said first subframe, wherein said MAClayer is to determine based on a MAC header of said first subframewhether the packet is intended to be received by the receiver and, ifthe packet is not intended to be received by the receiver, to cause thePHY to abort processing of the wireless communication packet, whereinthe receiver is to determine a power-down period based on a PhysicalLayer Convergence Procedure (PLCP) header when Transmit Opportunity(TxOp) termination is implemented, or based on a duration field of theMAC header of the first subframe when TxOp termination is notimplemented, and to power down one or more receiver components for thepower-down period; a central processing unit (CPU); a memory unitincluding a Read Only Memory (ROM); a Bluetooth (BT) system configuredto be used in conjunction with the receiver, the BT system, the PHYlayer, the MAC layer, the CPU, and the memory unit further beingenclosed in a common packaging.
 33. The device of claim 32, furtherincluding a Global Positioning System (GPS).
 34. The device of claim 32,wherein the device includes a smartphone, a tablet or a router.